Because of operating system conflicts that can result from different hardware configurations, Server Image was not intended to copy or image a hard disk that will be used in a system with different hardware configurations.
If you create an image on one machine and you want to restore the image on a machine with a different configuration (for example, a different motherboard or video card), the operating system may not boot correctly. Therefore, we recommend imaging and restoring to identical hardware configurations.
Create New Folder
Enter the name of the new folder you want to create in the Folder Name field.
Note: The folder name can be an entire path.
For example:
E:\IMAGES\TEMP
If the folder E:\IMAGES does not exist, the entire path will be created.
Create: Preparation
Before running Server Image, PowerQuest recommends that you do the following:
--Run a disk utility such as CHKDSK /F (Windows NT Workstation or Windows 2000 Professional) on each partition of the source drives to check for file system errors.
--Verify that each FAT partition containing OS/2 extended attributes has a minimum of 5 MB of unused space within the partition if it will be resized during the restore process.
--Create Server Image rescue diskettes.
Create: Create Image Advanced Options
The Create Image Advanced Options dialog box appears when you click Advanced Options from the Ready To Create Image File screen.
--Check for File System Errors - Clear the Check for File System Errors check box if you want to disable error checking.
If you have already used a disk utility program such as ScanDisk to check your hard disk for errors, it is not necessary to have Drive Image check for file system errors. Clearing Check for File System Errors saves time in copying the partitions.
If you did not run a disk utility program before loading Server Image, leave Check for File System Errors selected.
--Disable SmartSector Copying - Server Image
s SmartSector technology speeds up the copying process by only copying clusters and sectors that contain data. However, in some cases, such as high-security environments, it may be desirable to copy all clusters and sectors in their original layout, whether or not they contain data.
If you want to copy both used and unused clusters and sectors, select Disable SmartSector Copying. Disabling SmartSector Copying increases processing time.
--Password Protect Image File - To password-protect your image file, click Password Protect Image File, then type a password in the Password text box. To change or undo a password, use the Server Image File Editor.
Store image file passwords in a safe place. If you forget the password, you cannot restore the file.
--Split Image File Into Multiple Files - Sometimes it is useful to force Server Image to split a large image file into smaller files. To do so, click Split Image File Into Multiple Files, then specify the maximum byte size for each file in the File Size (bytes) field. If you want to save the files to CDs, specify a file size of 650,000,000 bytes (approximately 650 MB) or less.
Create: Compress Image File
No Compression is generally the fastest method for creating an image file and is useful if storage space is not an issue. Server Image selects No Compression by default.
Low offers a 40% average compression ratio.
High offers a 50% average compression ratio.
Tip: If you are saving your image file to a busy network disk or to a relatively slow removable media device, compression may be faster than no compression since there is less data to write to the file.
Create: Ready to Create Image FileP
Server Image displays all the information you have entered to this point.
1. If you want to modify any settings, click Back to make changes.
2. Click Advanced Options to set such options as disabling file system error-checking or password-protecting your image file.
3. Click Finish to begin creating the image file.
Note: If Server Image detects that you are saving your image file to a floppy disk or removable media, it enables a media-spanning feature that spreads the image file over a series of disks. Server Image permits you to span a maximum of 50 disks with a limit of 12 partitions per image file. You must have at least 100K of available space on each disk in the series. If you use the media-spanning feature, be sure to number the disks in order, since you must insert them in sequence when restoring the image file.
WIZ_NAME_IMAGE
HELP_CREATE_WIZ_SRC_DRIVE
HELP_CREATE_WIZ_SRC_PARTS
HELP_DIRECTORY_SERVICE
HELP_GENERAL
HELP_RESIZE_MAIN
HELP_RESIZE_OPTIONS
HELP_RESIZE_SUB
HELP_RESTORE_METHODS
Create: Name Image File9
Type the desired path and image filename in the Image File field, for example: D:\MYIMAGE.PQI.
Note: Server Image uses .PQI as the default image filename extension.
IMPORTANT: You must save your image file to a partition that you are NOT including in your image file.
You can also click Browse to browse the directory tree for your desired path and/or filename. If you select a pre-existing image file, the following message appears: "<Image Filename> exists. Do you want to overwrite it? Yes/No." If you select Yes, Server Image immediately deletes the existing file.
You can save your image file to any physical or logical disk which has a drive letter. That includes floppy drives, secondary hard drives, network drives, and removable media storage devices such as Jaz, Zip, SyQuest drives, and so forth.
Create: Select Source Drive
If your computer has more than one hard disk, select the disk that contains the partitions you want to include in the image file.
Create: Select Source Partitions
Select the source disk partitions you want to include in the image file, or click Select All to automatically select all partitions.
To deselect partitions, re-click a selected partition or click Select None to deselect all partitions at once.
Browse Directory Tree)
The Browse feature lets you browse for existing image files on your system.
To access an existing file, you can either enter the name in the Image File field or click Browse to browse the directory tree for the file.
In the Open Image File dialog, other image files in the current directory are displayed in the list box below the File Name field. To quickly access an existing image file, double-click on the desired file.
The List File Type drop-down list box determines the type of files that are displayed in the File Name list box. Selecting the " *.* " extension displays all files in the current directory. To list only image files, select the ".PQI" file extension.
The current directory is shown in the Folders field. Your file will be saved to this folder. If you want to save your image file to a different folder, select (click) the desired folder in the list box below the Folders field. Double-click a folder to display its contents.
The Drives drop-down list box displays the currently selected disk. Selecting a different disk displays that disk's file names and directories in their respective fields.
The Image File Comments field updates with comments when a file name is selected in the list of files. Click Properties for detailed information about the selected image file.
General Help
Server Image provides context-sensitive help for all windows and dialog boxes. Click the Help button to access help information. To close a Help window, click the Close button. To display a different topic, select Show Index, select the desired topic, and then select Show Topic.
Resize Source Partition(s)(main window)
If the destination partition or unallocated space is not large enough to accommodate the partitions you want to restore, or if you are restoring the image file to a larger disk and want to set a specific size for partitions rather than use the proportional resize option, you can click Resize Source Partition(s) to specify different sizes for restored partitions. To resize partitions,
1. Click Resize Source Partition(s).
The Resize Partitions window appears.
The Selected Source Partition(s) group box displays the partitions you selected to restore.
2. Click Resize to access a dialog where you can enter a new size for the selected partition.
Resize Options
The following options are available when restoring partitions if the unallocated space on the destination disk is greater than the space required by the partitions.
1. Automatically resize partitions proportionally to fit.
Mark this option to allow Server Image to automatically expand the partitions in equal proportions to occupy the destination disk's remaining unallocated space.
2. Leave remaining unused space.
Mark this option if you want to leave any remaining free space unused on the destination disk after the partitions are restored.
3. Resize partitions manually to fit.
Mark this option to display the Resize Partitions window where you can manually set the size of the partitions to fit in the destination disk's remaining unallocated space.
Resize Partition Dialog
After you click Resize in the Resize Partitions main window, the Resize Partition dialog appears.
The Maximum Size field displays the largest possible size the source partitions can have and still fit in the destination space.
The Minimum Size field shows the smallest possible size the source partitions can occupy.
To enter a new size for the selected partition:
1. In the New Size field, enter a number that is less than the Maximum Size and greater than or equal to the Minimum Size.
2. Click OK.
Since partitions must end on a cylinder boundary, Server Image rounds the New Size up to the next cylinder boundary.
3. Click Accept.
Later, when you restore the image file, Server Image resizes the partition.
Restore: Methods
If you create an image on one machine and you want to restore the image on a machine with a different configuration (for example, a different motherboard, video card, and so forth), the operating system may not boot correctly. Therefore, we recommend restoring to similar hardware configurations.
To restore selected files from a compressed or spanned image file, see chapter 3 "Restoring Image Files" in the Server Image User Guide.
HELP_RESTORE_WIZ_ADV_OPTIONS
HELP_RESTORE_WIZ_DEST_DRIVE
HELP_RESTORE_WIZ_DEST_SPACE
HELP_RESTORE_WIZ_FINISH
HELP_RESTORE_WIZ_IMAGE_PARTS
HELP_RESTORE_WIZ_SELECT_IMAGE
HELP_TOOLS_CREATE_EXTENDED
Restore: Restore Image Advanced Options
The Restore Image Advanced Options group box appears when you click Advanced Options at the Ready To Restore Image File screen. The following options are available from the Restore Image Advanced Options group box:
1. Check for File System Errors
This is marked by default to verify the partitions restored contain no errors after restoration.
2. Skip Bad Sector Check
This is marked by default to save time in restoring the image file. Although most drives do not have bad sectors, the potential for problems increases during the lifetime of the hard disk. If you have an older hard disk, it is wise to enable bad-sector checking by deselecting Skip Bad Sector.
3. Verify Disk Writes
Mark the Verify Disk Writes check box if you want to enable disk write verification.
Note: Disk write verification is not critical to safely restore image files. Enabling disk write verification can significantly slow down the image file restore process.
4. Hide Partition After Restore
Most operating systems only allow one primary partition to be visible (bootable) at a time. If you are restoring an image of a primary partition and you do not want to make that partition your visible (bootable) partition, mark the Hide Partition After Restore box.
Restore: Select Destination DriveB
Select the disk to which you want to restore the image file.
Restore: Select Destination Partition or Unallocated Space
Select an existing partition or unallocated space (non-partitioned disk space).
If the destination partition or unallocated space is not large enough to accommodate the partitions you want to restore, or if you are restoring the image file to a larger disk and want to set a specific size for partitions rather than use the proportional resize option, you can click Resize Partitions to specify different sizes for restored partitions.
Restore: Ready to Restore Image File
Server Image displays all the information you have entered to this point.
To alter any settings, click Back to make changes.
If you want to enable bad-sector checking or hide partitions after restore, click Advanced Options.
WARNING: Restoring multiple logical partitions can cause the drive letters of subsequent partitions to change. This may make the computer unbootable or cause applications to fail.
Click Finish to begin restoring the image file.
If you assigned a password to the image file when you created it, the Get Image File Password dialog appears. You must enter the password to restore the image file.
Note: If Server Image detects that you are restoring your image file from a floppy disk or removable medium, it enables a media-spanning feature that is capable of reading the image file from a series of disks. As Server Image prompts you for each disk, make sure you insert the disks sequentially.
Restore: Select Image File Partitions to Restore
Select the image file partitions you want to restore, or click Select All to automatically select all partitions.
To deselect partitions, click a selected partition or click Select None to deselect all partitions at once.
Restore: Select Image File
In the Image File field, enter the complete file name of the image file you want to restore, or click Browse to browse the directory tree for the desired path and image file name.
Tools: Create Extended Partition
If you create an image of a primary partition and want to restore it as a logical partition, you must first have an extended partition on your hard disk.
Note: It is not necessary to manually create an extended partition when you restore an image of a logical partition. Server Image automatically creates an extended partition if one does not already exist.
To create an extended partition:
1. At the Server Image main screen, select Tools > Create Extended Partition.
2. If you have more than one hard disk on your system, select the disk you want from the Physical Drives drop-down list box.
3. Click on a free space.
If there is no unallocated space (unpartitioned area) on your disk, you must delete an existing partition to create unallocated space. For more information, see Tools: Delete Partition(s).
4. Click Create.
Server Image creates an extended partition in the selected unallocated space.
5. Click Close to return to the Server Image main screen.
HELP_TOOLS_DELETE_PART
HELP_TOOLS_DRIVE_INFO!
HELP_TOOLS_HIDE_UNHIDE_PART"
HELP_TOOLS_SET_ACTIVE#
BIOS_CYLINDER_LIMIT$
BOOT_CODE_BOUNDARY%
TECHNICAL_SUPPORT_HLP&
ERROR_MISC_3_38'
ERROR_DI
Tools: Delete Partition(s)
This feature deletes existing partitions to create free space on your hard disk.
WARNING: Be aware that deleting existing partitions DESTROYS any data they contain.
To delete partitions:
1. At the Server Image main screen, select Tools > Delete Partition(s).
2. If you have more than one hard disk on your system, select the disk you want from the Physical Drives drop-down list box.
3. Click on the partition you want to delete.
4. Click Delete.
You will be prompted to enter the current volume label.
5. Type the volume label exactly as it appears, then click OK. Drive Image deletes the partition.
6. Click Close to return to the Server Image main screen.
Tools: Display Drive Information
The Display Drive Information option lets you view information about the partitions on your current hard disk. You can view:
Drive letters
Volume (partition) labels
Color--coded volume (partition) types
Status (active partition)
Partition size
Used MB in partitions
Free MB in partitions
Primary or logical disk
Boot Code Boundary Markers--On the partition map, the first set of triangles from the left (blue) represent the DOS 2 GB boot code boundary. The second set of triangles from the left (black) represent the DOS 8 GB boot code boundary. The second set of triangles will not appear on the partition map if your hard disk is smaller than 8 GB.
If you have more than one hard disk on your system, select the disk you want to view from the Physical Drive drop-down list.
Tools: Hide or Unhide Partition(s)L
This feature allows you to protect partitions from unwanted user access. When you hide a partition, it is not assigned a drive letter the next time you boot your computer and therefore is inaccessible. Alternately, if you unhide a partition, it is assigned a drive letter the next time you boot your computer and becomes accessible again.
Before hiding and unhiding partitions, be aware of the following:
(a) Hiding or unhiding a partition can cause the drive letters of subsequent partitions to change. This may make the computer fail to boot or cause applications to fail.
(b) If your hard disk contains more than one primary partition, only one is visible by default. When you use the Set Active Partition feature, Server Image unhides the selected primary partition and automatically hides all other primary partitions.
(c) Because a hidden partition is not bootable or accessible, if you hide the partition where Server Image is installed, you must re-install Server Image on your new active (bootable) partition to run it again.
To hide or unhide partitions:
1. At the Server Image main screen, select Tools > Hide/Unhide Partition(s).
2. If you click on a visible partition, the Hide button is available. Click Hide to hide the selected partition. The partition status changes to "Hidden".
3. If you click on a hidden partition, the Unhide button is available. Click Unhide to unhide the selected partition. The partition status changes to "None".
4. Click Close to return to the Server Image main screen.
5. Click Exit to exit Server Image.
6. Reboot your computer.
Tools: Set Active Partition
The Set Active Partition feature allows you to make a primary partition the active (bootable) partition. Only one primary partition can be active at a time. To be bootable, a primary partition must be located on the first (master) disk, and it must contain an operating system. When your computer boots, it scans the partition table of the first disk to find the active partition, then boots from that partition.
WARNING: Before you set a partition active, be sure it is bootable. If it is not bootable or if you are not sure, locate the boot disk you created when you installed Server Image. If you restart your computer and it does not boot normally, you must boot from the floppy disk, run Server Image from the program disk you created during Server Image install, and set a different active partition.
To set a partition active:
1. At the Server Image main screen, select Tools > Set Active Partition.
2. Make sure that Disk 1 is selected in the Physical Drives drop-down list box.
3. Select a primary partition that is not currently active.
4. Click Set Active. The status of the selected partition changes to "Active".
5. Click Close.
6. Click Exit to exit Server Image.
7. Reboot your computer.
Understanding the BIOS 1024 Cylinder Limit:
The BIOS 1024 cylinder limitation exists because the start and end cylinder values in the partition table (and some BIOSs) have a maximum value of 1024. Because some operating systems such as DOS 6.22 use the CHS (Cylinder, Head, and Sector) values to address sectors on the disk, they cannot access sectors beyond the 1024 cylinder. When you start your computer the BIOS boots the operating system using the CHS values to locate the first sector of the bootable partition. If the partition starts past the 1024 cylinder, the BIOS may not be able to boot it because it cannot address a cylinder number higher than 1024.
Be aware that if you run Server Image from the rescue disks, you will not be able to see partitions that begin or exist beyond the 1024 cylinder boundary. You can use a Windows NT startup disk to avoid this limitation.
The partition map in Server Image displays an indicator at the 1024 cylinder mark, so you can see where your partitions are located relative to the 1024 cylinder limit. Be sure that all OS partitions on a disk start prior to cylinder 1024. This ensures that you can boot the OS. Also, use caution when moving a bootable partition; if the partition is moved beyond cylinder 1024 it may nolonger be bootable. To fix this problem you can move the partition below the 1024 cylinder marker.
Understanding the 2 GB Boot Code Boundary
An OS
s boot code is stored in both the master boot record (MBR) and the partition boot record, enabling the OS to boot properly. In some OSs, however, this boot code is written is such a way that it inadvertently imposes a limit on the location of both the partition boot record and the files needed to boot the OS.
DOS (versions 6.x and earlier) and Windows NT (versions 4.0 and earlier) are both affected by this boot code limitation. When booting these two operating systems, the cylinder-head-sector (CHS) address of the beginning boot code sector must be calculated in order to retrieve the sector
s information and load and execute the next part of the boot process. The CHS value for the needed sector is calculated as follows:
Sector Number - Sectors Per Track
Because of the way the boot code is written, the product of this calculation must fit in a 16-bit register. The largest value a 16-bit register can contain is 64K. If the number is larger than 64K, the number is truncated, resulting in an incorrect value that skews the remaining calculations. The boot process fails to load and execute the needed sector, thus preventing the OS from booting.
Most current hard disks have 63 sectors per track, creating a 64K boot code boundary at 2 GB. If your disk is older or uses disk overlay software, this boundary may be lower.
If a partition begins or extends beyond this boundary, the CHS value of the partition
s boot code sector cannot be correctly calculated; therefore, the partition and its OS cannot boot.
This same limit applies to the DOS IO.SYS file and the Windows NT file, NTLOADER.EXE. If either of these files are installed or moved beyond the 64K boot code boundary, the corresponding OS fails to boot. To boot properly, DOS requires that the first three sectors of IO.SYS be below the 2 GB boot code boundary.
When you attempt to set a partition active, it must be within the boot code boundary required by the operating system. If the operating system has a 2 GB boot code boundary, you can use the small, triangle indicator on the partition map in the Server Image window to determine if the partition will be bootable.
TECHNICAL SUPPORT
Before contacting our technical support department, please try to resolve your problem by using this help, the user guide, the README file, and PowerQuest
s corporate web site.
-Your problem may be resolved by applying the most recent patch or upgrade of the software. You can download patches and upgrades from http://www.powerquest.com/updates.
-Your product serial number is required to obtain technical support.
-If you received a demo or trial version of the PowerQuest software, you are not entitled to complimentary technical support.
Term of Technical Support
Technical support is available to all registered users throughout the life of the product, which began when PowerQuest released the software to manufacturing and ends six months after the release of the next version of the software or when PowerQuest discontinues its development.
Upon registration, PowerQuest provides 45 days of complimentary technical support from the day of your first call.
Corporate Web Site
The Technical support web site, http:/support.powerquest.com, includes an overview of support options, an e-mail support request form, a list of error messages and information to resolve problems you encounter, and answers to frequently asked questions about the product.
E-mail
Language -- E-mail address (for specific technical problems)
Dutch -- eurots@powerquest.com
English -- help@powerquest.com\ OR eurots@powerquest.com
French -- france@powerquest.com
German -- germany@powerquest.com
Italian -- italian@powerquest.com
Portuguese -- latina@powerquest.com
Spanish -- spanish@powerquest.com
To obtain e-mail technical support for specific technical questions, you can fill out the form at support.powerquest.com (available in English only).
E-mail on Demand
PowerQuest maintains an e-mail on demand system to resolve common problems. You can view a list of available documents at http://support.powerquest.com. To request one of the documents, send an e-mail message to support@powerquest.com with the index number of the document in the subject of the message. You can only request one document per e-mail message. E-mail on demand documents are available in English only.
USA -- +1 (801) 437-4218
Europe -- +31 (0)20 581 9270
Fax a description of your problem to the technical support fax number. This service is available in the U.S., Canada, and Europe 24 hours a day, 7 days a week. PowerQuest technicians try to respond to all fax requests within 24 hours.
Telephone
Language -- Location -- Number
Dutch -- Netherlands -- +31 (0)20 581 3906
English -- Netherlands -- +31 (0)20 581 3907
English -- UK -- +44 (0)17 1341 5517
English -- USA -- +1 (801) 226-6834
French -- France -- +33 (0)1 69 32 49 30
German -- Germany -- +49 (0)69 66 568 516
Italian -- Italy -- +39 (0)2 45 28 1312
Portuguese -- USA -- +1 (801) 226-6834
Spanish -- Spain -- +34 (0)91 662 31 46
Spanish -- USA -- +1 (801) 226-6834
The USA call center is open Monday through Friday, 7 a.m. to 6 p.m., MST/MDT. Our European call center, located in the Netherlands, is open Monday through Friday from 9:00 to 18:00, CET.
Postal Service Mail
PowerQuest Corporation
P.O. Box 1911
Orem, Utah 84059-1911
U.S.A.
Europe
PowerQuest Customer Service
P.O. Box 58287
1040 HG
Amsterdam
The Netherlands
Please include a description of your problem. Also include a return address, a daytime phone number, or other relevant contact information.
Miscellaneous Errors (3-38)
#3 Not enough memory
The DOS Server Image executable running under DOS requires a minimum of 400KB of memory in the first 640KB of the computer's address space (conventional memory) and 8MB of total memory. If you don't have enough conventional memory, see "Using the F8 Key to Keep Programs from Loading" in the Troubleshooting appendix of the Server Image User Guide.
#8 Could not allocate/deallocate DOS real mode memory
The DOS Server Image executable running under DOS requires some memory in the first 1MB of the computer's address space (Server Image uses a DOS extender). If not enough memory is available, Server Image cannot access the hard disk. If you don't have enough conventional memory, see "Using the F8 Key to Keep Programs from Loading" in the Troubleshooting chapter of the Server Image User Guide.
#23 Unsupported version of operating system
The operating system versions that are required to run Server Image are listed in System Requirements in the Introduction of the Server Image User Guide.
#36 DPMI Server error
Server Image DOS executables use a DOS extender. This error indicates a failure during a call made from Server Image through the DOS extender (to DOS or to the BIOS). The DOS extender may be in conflict with other programs that use extended memory. DOS would load the conflicting programs from your CONFIG.SYS or AUTOEXEC.BAT file during the normal boot sequence.
You may be able to resolve this problem by pressing <F8> while booting DOS. After DOS boots and starts to read the commands from your CONFIG.SYS and AUTOEXEC.BAT files, DOS will ask if you want to execute each command. When you see commands that load device drivers or TSR programs that you think might be conflicting with the Server Image DOS extender, answer N (no) to tell DOS not to execute that command (not to load that software into memory). You will often be able to find a program configuration that will enable Server Image (the DOS extender) to run without error.
SK_ACCESS_40_56(
ERROR_PARTITION_100_199)
ERROR_CHECK_500_599*
ERROR_HPFS_1000_1500+
ERROR_NTFS_1500_1699,
ERROR_MISC_1701_UP-
ERROR_FAT_2000_2099
Disk Access Errors (40-56)
Errors in the 40-56 number range indicate that accessing your disk is not possible, and, often, are the result of hardware problems. Some problems may have simple solutions. For other problems, the only solution may be replacing the hard disk. When possible, Server Image detects major errors before any changes have been made so you can back up your data before replacing the hard disk.
#49 Write fault
#50 Read fault
Server Image is unable to write to/read from a specific sector on the hard disk. There are a number of possible causes of this error:
a. If your PC beeps or displays a black box in the middle of the screen, virus protection is enabled in your computer's BIOS. Disable virus or boot sector protection in the BIOS.
b. A virus protection application (which may be a TSR or DLL program) is in use. Disable the application before using Server Image.
c. There is a bad sector on the hard disk (this is usually the case with only older hard drives). Run ScanDisk on the hard disk to perform a surface scan to verify the existence of bad sectors. If your disk has bad sectors, we recommend you replace it.
d. You have set up disk mirroring with PC-Tools. Disable the disk mirroring option.
e. Your caching controller card is not set up properly.
Partition Table Errors (100-199)
Errors in the 100-199 number range are partition table errors. For general information about solving this type of error, see "Resolving Partition Table Errors" in the Troubleshooting appendix of the Server Image User Guide.
#100 Partition table is bad
The master boot record (MBR) can contain, at most, one extended partition, and each extended partition boot record (EPBR) can contain, at most, one link to another EPBR. This error occurs when a partition table violates the foregoing rule. Since any modifications Server Image makes may decrease the amount of data that is recoverable from the hard disk, Server Image will not recognize any of the hard disk's partitions. You must create new, error-free partition tables to resolve your problem. See "Partition Tables and Viruses" in the Troubleshooting appendix of the Server Image User Guide.
#104 No sectors in partition
No partition should contain zero sectors. Delete the partition before using Server Image.
#105 Partition starts on wrong boundary
The hard-disk partition table contains erroneous values. Server Image expects FAT, NTFS, and HPFS partitions to begin and end on the boundaries used by FDISK. If they do not, the disk may be partially corrupted. In this circumstance, if Server Image were to make any modifications it might cause the loss of data. Therefore, Server Image will refuse to recognize any of the hard disk's partitions. To resolve this problem, see "Resolving Partition Table Errors" in the Server Image User Guide.
#106 Partition doesn't start with sector one
See error #105.
#107 Partition begins after end of disk
This error can occur when you are running Server Image on a hard disk that uses more than 1,024 cylinders. Running from the rescue disks, Server Image is restricted by the BIOS 1,024 cylinder limit. If any partitions extend beyond the limit, Server Image cannot safely operate on the hard disk.
This error can also occur if a partition erroneously extends beyond the physical end of the hard disk. This may happen if the hard disk has been used on a different computer or with a different hard-disk controller or if BIOS settings have been changed. Be advised that the physical geometry of the hard disk may differ from the logical geometry assigned to the hard disk by the operating system.
#108 Partition doesn't end at end of cylinder
See error #105.
#109 Partition ends after end of disk
See error #107.
#110 Partition table number of sectors is inconsistent
The hard-disk partition table contains two inconsistent descriptions of the number of sectors on the hard disk. This error is serious if both DOS and another operating system use the hard disk. Because DOS uses one description and other operating systems may use the other, data loss is likely once the partition is almost full. To resolve this error, see "Resolving Partition Table Errors" in the Server Image User Guide.
#111 Logical partition starts outside Extended
The hard-disk partition table contains erroneous values. All logical partitions must be totally contained within the extended partition. To resolve this error, see "Resolving Partition Table Errors" in the Server Image User Guide.
#112 Logical partition ends outside Extended
See error #111.
#113 Partitions overlap
The hard-disk partition table contains erroneous values. If data partitions overlap, writing to one may destroy data in another. This error is sometimes the result of an OS/2 FDISK bug. If free space exists within the extended partition, OS/2's FDISK program allows a primary partition to be created that overlaps the extended partition. A logical partition is subsequently created in the space occupied by the overlapping primary partition.
If a primary partition overlaps the end of the extended partition, but does not overlap any logical partitions within the extended partition, the problem can be remedied by patching the partition table. Only qualified individuals should attempt this repair! An incorrect patch could destroy all data on the hard disk! In most instances, you should resolve the problem as explained in "Resolving Partition Table Errors" in the Server Image User Guide.
#116 Partition table Begin and Start inconsistent
The hard-disk partition table contains two inconsistent descriptions of the partition's starting sector. This error can occur if the operating system reports a hard-disk geometry that is different than the geometry in use when the partition table was written. Possible causes of the hard-disk geometry changing are:
a. Different operating systems (for example, DOS and OS/2) report different hard-disk geometries.
b. You boot from a diskette that loads a different driver than is loaded when you boot from the hard disk.
c. Upgrading the operating system (for example, from OS/2 2.x to OS/2 Warp) causes a different driver to be used.
d. The hard disk or controller has been changed.
e. The BIOS has been upgraded.
f. The BIOS LBA setting has been changed.
g. There is a partition table virus present on the hard disk.
In most instances, you should resolve the problem as explained in "Resolving Partition Table Errors" in the Server Image User Guide. You can also use a virus scanning program to remove any partition table virus.
Data loss is possible if the number of heads or sectors per track has changed since you first created your partitions.
#120 The logical drive chain is incompatible
This error occurs under some OSs when logical partitions are not chained together in the expected order. DOS, OS/2, Windows 95/98/Me, and Windows NT require that logical partitions be chained together in ascending order. Some other operating systems do not require this. For example, some versions of the Linux FDISK utility chain logical partitions together in the order they are created. This error message identifies a very dangerous situation; using the DOS FDISK in this situation can cause loss of one or more partitions.
For solutions to this problem, see the instructions in "Resolving Partition Table Errors" in the Server Image User Guide.
If you decide to back up your data and recreate your partitions, you may have to use the same partitioning program that you used to create the partitions in order to delete them.
#121 The first sector of the drive cannot be read
The first sector of the hard disk (cylinder 0, head 0, sector 1) contains the master boot record (MBR) and the primary partition table. Server Image cannot make changes to this hard disk because an error occurred when it read the first sector. See error #50 for information on resolving this error.
#122 A bad sector was found in the current or new partition area
The partition cannot be moved safely because there is a bad sector in the new or current partition area. When you see this error message, the move operation will be aborted before any corruption can occur. Try moving the partition to a different place. If your hard disk has bad sectors, we recommend that you replace the hard disk.
Check Errors (500-599)O
Check errors occur when Server Image checks the integrity of a partition. For useful general information about resolving these errors, see "Resolving Check Errors" in the Server Image User Guide.
#500 Subdirectory is corrupted
This error message reveals the name of the corrupted subdirectory. Back up the contents of that directory and its subdirectories. You can then delete the corrupted subdirectory.
#501 Cross-linked files were found
ScanDisk or CHKDSK should be able to find these errors and correct them.
#506 Not enough free space on partition to shrink
Some free space (which is dependent on the hard disk's current contents) is required to resize a partition smaller. Delete unneeded and duplicate files in the partition and then attempt the operation again.
#508 As specified, the operation does not change the partition
You have entered a value that is the same as or (when rounded to the required cylinder boundary) rounds to the same as the partition's present value. Enter a larger change.
#509 A bad sector was detected in the current or new FS area
In order to perform the resize operation that you requested, Drive Image attempted to expand the file system area. However, the program found a bad sector in the new area. Try moving the partition before you resize it. No corruption will occur when you encounter this error.
#510 The version of the file system is not supported
An updated version of Server Image is required to operate on this new version of the file system. Visit www.powerquest.com for information about updated versions of Server Image.
HPFS Check Errors (1000-1499)
Check errors occur when Server Image checks the integrity of a partition. For useful general information about resolving these errors, see "Resolving Check Errors" in Appendix B of the the Server Image User Guide.
#1015 System sector not marked unavailable
This error may indicate that there are open files on the hard disk. Shut down and restart OS/2, booting from diskettes. If this does not resolve the problem, run OS/2's CHKDSK program. This error message may also indicate that a file is listed with a file length of zero. OS/2's CHKDSK program will not fix this problem. As a last resort, delete the offending file.
#1027 Could not account for all sectors
This error may be resolved in one or more of the following ways:
a. If you are working with an HPFS386 partition, check the technical support area of PowerQuest's Web site (www.powerquest.com) for more information.
b. If CHKDSK has created any FOUND.000 or *.CHK files, delete them.
c. If the error message indicates the name of the offending file, delete it.
d. Turn off the disk-mirroring option in PC-Tools.
e. If none of the above solutions works, back up the partition, delete it, recreate it, and restore the data.
#1045 Stac volume detected delete-Stac volume before converting
This error message occurs when you attempt to convert a partition to HPFS, and the existing partition contains a STAC volume. Stacker cannot access a STAC volume that is on an HPFS partition. Delete the STAC volume from the partition before converting to HPFS.
NTFS Check Errors (1500-1699)
Errors 1500-1699 are NTFS-specific error messages. In this context, "attribute" does not mean read-only, hidden, system, and so on. Rather, "attribute" means one of a file's data streams. Check errors occur when Server Image checks the integrity of a partition. For useful general information about resolving these errors, see "Resolving Check Errors" in the Troubleshooting appendix of the the Server Image User Guide.
#1501 Wrong version of NTFS
The partition was created using a version of the NTFS file format that Server Image cannot work with.
#1503 Bad NTFS cluster size
The NTFS cluster size must be 512, 1,024, 2,048, or 4,096 bytes.
#1512 Restart record mismatch
The two restart entries in the journal file are different. This may happen if Windows NT is not properly shut down. To fix this problem, restart Windows NT and shut it down using the Shut Down command.
#1516 Partition improperly dismounted
The partition dirty flag is set in a restart record in the journal file. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing the partition. Reboot Windows NT and execute CHKDSK /F to repair the damage.
#1527 Bad update sequence number
A buffer contains mismatched update sequence numbers. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing to the partition. Reboot Windows NT and execute CHKDSK /F to repair the damage.
#1529 Information mismatch in directory entry
A file attribute stored in a file record is different from the attribute stored in its directory entry. If this error is in a system file (file 0-10), Windows NT's CHKDSK program will not fix it, but Windows NT will rebuild the root directory on the partition the next time the operating system is started.
#1538 Can't find contiguous space to move
The partition does not contain enough contiguous free space to hold the new copy of a file that must be contiguous. You will normally encounter this error when you use the Resize option to resize a partition smaller.
#1539 File size mismatch
The size of a system file (file 0-10) recorded in its file record does not match either the size recorded in its directory entry in the root directory or the size of its data stream.
#1544 External attribute list in external attribute
An external file record has an external attribute list.
#1545 File attributes out of order
The attributes in a file must appear in order of increasing numeric type.
#1546 Attribute neither resident nor nonresident
The attribute resident flag has a value other than resident or nonresident.
#1547 Wrong run limits
A run has more clusters than the difference between its highest and lowest cluster.
#1548 File table has fewer than 16 entries
The file table must have at least 16 entries.
#1549 File table has more than 4 billion entries
The file table must have fewer than 4 billion entries.
#1644 Bad system file sequence number
A system file has a bad sequence number. System files must have a sequence number from 0 to 10. A partition with this problem may pass a run of Windows NT's CHKDSK program, but Windows NT will not mount the partition the next time the operating system is started.
#1647 Error in root directory index
There is an error in the root directory's index. Running Windows NT's CHKDSK program will not fix this problem, but the Windows NT operating system will automatically rebuild the root directory on the partition the next time it is started.
Miscellaneous Server Image Error Messages
#1801 Err partition not found
Did not find requested partition in image file.
#1805 Err write failed
Error encountered while writing image to file. This error usually occurs when Server Image runs out of space in the partition to which it is writing an image file.
#1808 Err buffer too small
Buffer too small to read in partition bitmap.
#1810 Err open failed
Could not open image file.
FAT Check Errors (2000-2099)1
Check errors occur when Server Image checks the integrity of a partition. For useful general information about resolving these errors, see "Resolving Check Errors" in the Server Image User Guide.
#2001 FAT copies are not identical
Run SCANDISK to fix this error. This problem may also be caused by a virus. Run a virus checker and remove the virus if possible.
#2005 One or more lost clusters were found
Run SCANDISK or CHKDSK to fix this error.
#2012 Formatted FAT file system too big for partition
This error can be caused by the following circumstances:
a. The number of sectors in the partition is larger than 65,536, and the bsHugeSects field of the boot sector ("Big total number of sectors" in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows.
b. The number of sectors in the partition is less than 65,536, and the bsSects field of the boot sector ("Total sectors on disk" in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows.
This situation can result in data loss when the FAT file system tries to use space outside the partition that does not exist or that belongs to another partition. Since file data may exist outside the partition boundary, you cannot fix the problem by simply patching the boot sector.
To correct the error, back up all data on the partition, delete the partition, recreate the partition, and restore the data. Alternately, it has been reported that you can use Norton Disk Doctor to fix this problem.
#2013 A component of FAT geometry is bad
This error can be caused by the following circumstances:
a. The number of clusters on the hard disk is greater than the FAT limits allow. This can result from bad values in the boot sector for the number of sectors, FATs, root entries, reserved sectors, and sectors per cluster.
b. The number of sectors in the FAT is not large enough to hold the number of clusters present on the hard disk.
A qualified consultant may be able to fix the hard disk by performing simple patches. Alternately, you can back up the data on the partition, delete the partition, recreate the partition, and restore the files.
#2024 The OS/2 Extended Attribute file is corrupt
This error is caused by any program that mistakenly writes to or overwrites the OS/2 Extended Attribute file. If this error occurs, you should back up your data, delete the partition, recreate the partition, and restore your data.
Copyright 1994-2000, PowerQuest Corporation. All rights reserved.
(.txt)